Skip to content

Conversation

@wzxxing
Copy link
Contributor

@wzxxing wzxxing commented Oct 7, 2025

Summary

Changes

Please provide a summary of what's being changed

at 18:13:04 ❯ aws-mcp-proxy --help
usage: aws-mcp-proxy [-h] [--service SERVICE] [--profile PROFILE] [--region REGION] [--read-only] [--log-level {DEBUG,INFO,WARNING,ERROR,CRITICAL}] [--retries [0-10]] endpoint

AWS MCP Proxy v0.0.0

positional arguments:
  endpoint              SigV4 MCP endpoint URL

options:
  -h, --help            show this help message and exit
  --service SERVICE     AWS service name for SigV4 signing (inferred from endpoint if not provided)
  --profile PROFILE     AWS profile to use (uses AWS_PROFILE environment variable if not provided)
  --region REGION       AWS region to use (uses AWS_REGION environment variable if not provided, with final fallback to us-east-1)
  --read-only           Disable tools which may require write permissions (readOnlyHint True or unknown)
  --log-level {DEBUG,INFO,WARNING,ERROR,CRITICAL}
                        Set the logging level (default: INFO)
  --retries [0-10]      Number of retries when calling endpoint mcp (default: 0) - setting this to 0 disables retries.

Examples:
  # Run with your endpoint
  aws-mcp-proxy <SigV4 MCP endpoint URL>

  # Run with custom service and profile
  aws-mcp-proxy <SigV4 MCP endpoint URL> --service <aws-service> --profile default

  # Run with write permissions enabled
  aws-mcp-proxy <SigV4 MCP endpoint URL> --read-only

@acmlau can also use the version number as the source of truth to add MCP clientInfo

User experience

Please share what the user experience looks like before and after this change

Checklist

If your change doesn't seem to apply, please leave them unchecked.

  • I have reviewed the contributing guidelines
  • I have performed a self-review of this change
  • Changes have been tested
  • Changes are documented

Is this a breaking change? (Y/N)

  • Yes
  • No

Please add details about how this change was tested.

  • Did integration tests succeed?
  • If the feature is a new use case, is it necessary to add a new integration test case?

Acknowledgment

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@wzxxing wzxxing requested a review from a team as a code owner October 7, 2025 16:13
@wzxxing wzxxing merged commit 0a6e54f into aws:main Oct 7, 2025
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants